ScanCom EIE

The ScanCom EIE is designed to interface with much of the ScanCom device’s feature set while providing an organized data structure from the user’s perspective. Along with standard EIE functionality, the ScanCom EIE includes multiple levels of device security, custom error handling, and an editor for device-level data groups that can be configured specifically for a device instance.

Note: If you use the ScanCom EIE, devices return data in metric units, not in imperial units.

Device Definition Information

Device Security

Successive security definitions override previous definitions. If no security is defined in the device template file or device properties, the factory default on the device is used.

Device security can be configured at any of three levels:

Factory default
Device template file
Security fields in device properties (device-level security)

The security definition in the device template file can be configured using the idWrite, pwWrite, idRead, and pwRead attributes in the deviceDefinition element.

Device Attributes

The deviceDefinition element of the ScanCom device template file includes three attributes that are specific to the remote device.

The ADEPT-7 (application layer) application address is specified in the DTF using the A7_applicationAddress attribute.

The ADEPT-4 (transport layer) network identifier is specified in the DTF using the A4_networkid attribute.
The Trusted A4 Device Address is specified in the DTF using the trustedId attribute.

These values must be entered in hex in the device template file and must match the values as configured on your remote device.

Session Error Recovery

For ScanCom devices using ADEPT protocol version 4.0, if there is an error (such as bad comms) that prevents the driver from sending the logout or disconnect to the RTU, the session error recovery functionality will get the device out of this error state. The following lines must be added to the device template file to enable this function.

</extendedFeatures>

Error Codes

The device template file includes a ptDataError element that defines how error states are handled for returned data values. Any number of status elements can be added, where each refers to a different error value (errValue). Here status is a placeholder for the name of the error state.

<status errValue=val

updateValue=true|false

setUnreliable=true|false

setUserBitPos=bit >

</status>

</ptDataError>

Attribute	Description
errValue	The error code on the device that corresponds to the value’s error status
updateValue	Whether or not to update the value when this error status is returned. For some error states, return values can be unpredictable.
setUnreliable	Whether or not to set the unreliable bit to true when this error status is returned for a value
setUserBitPos	The user bit to set when this error status is returned for a value

Specifications

The following table lists and describes EIE specifications.

Manufacturer	Barton
Protocol(s)	ADEPT Protocol, versions 3.4 and 4.0
Model(s)	Firmware versions 3.4 and 4.1
Required Files	CxDdsScanComEditors.dll UisScanComDeviceDriver.dll
Sample Templates	ScanCom.dtf ScanCom_V342.dtf ScanCom_V413.dtf
Cryout Support	No
FMS Support	Yes, using FMS Legacy EFM data items Note: In cases where only GMR support was previously available, CygNet Measurement now provides equivalent data support using FMS Legacy data items. If you were previously using GMR data items, you must update to use FMS Legacy data items. Update options are provided as part of your software upgrade procedure. See the CygNet Upgrade Procedure for more information.
Listen Mode	Yes
64-bit Support	Yes. See 64-bit Device Drivers.

For more information, see sample device template files and manufacturer documentation.

Editor – Device Page

Data Groups

UIS Command Component Parameters

Data Group Types

Device-Level Data Groups

Ordinalized Data Groups

FMS Legacy Configuration Data Mapping